Skip to main content
This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal

HCL Notes/Domino 8.5 Forum (includes Notes Traveler)

HCL Notes/Domino 8.5 Forum (includes Notes Traveler)

Previous Next
Subject: Strange Full Text Indexing problem
Feedback Type: Problem
Product Area: Domino Server
Technical Area: Functionality
Platform: Windows
Release: 8.5.3
Reproducible: Always

We have a moderately large database of 1.640 MB with document count fluctuating betweeen 6000 and 9000, for which it has not been possible to build a full text index.

Note: the database is in constant use, with some 500-1000 updates every 30 minutes.

There have been several attempts to get this database FT index up and running.
What happens is this: every time the index is thrown away and a new FT index is built, the process begins normally.

Monitoring the database properties FTI tab, the index size built up to 4G then restarted at 0, and then stopped at 2,521, at which time the view Search bar changed from "Indexing" to "Not indexed". Meanwhile, the Server tasks are still showing a Full Text Indexer task that is busy rebuilding the FTI of database XXX.
Going to the server's directory, we see:
two temporary files -- ftgdocid.tmp, size 1 KB, and ftgdocof.tmp, size 6.775.562 KB.

This is a seriously large size, but the database properties index tab still shows size 2.521.

Half an hour later, the temporary files were updated --
ftgdocid.tmp, 1 KB
ftgdocof.tmp, 6.776.302 KB
with 2.581 MB in database properties index tab.

Meanwhile, Server Tasks show the FTI process hanging and demanding 92+% of server CPU time, the database is showing as "Not indexed", and there is a FT folder that can not be deleted because indexing is still in progress.

Questions: Is it possible that the indexing process has slowed to a crawl because of memory issues?
What action will fix this issue?

Note: if the process requires a very long time, there might never be enough time for it to complete before it conflicts with daily server maintenance tasks.

Does anyone have any suggestions?


Feedback number WEBB9ZXMM8 created by ~Tanita Fezponevitchobu on 09/01/2015

Status: Open
Comments:

Strange Full Text Indexing problem (~Tanita Fezpone... 1.Sep.15)
. . Re FTI issue (~Fred Umkivitch... 2.Sep.15)
. . . . Update -- FTI memory issue (~Tanita Fezpone... 4.Apr.16)




Printer-friendly

Search this forum

Member Tools


RSS Feeds

 RSS feedsRSS
All forum posts RSS
All main topics RSS